Mitigation of geolocation based data remanence problems

ABSTRACT

A method, system, and/or computer program product modify a computer resource that has been moved to a new geolocation. One or more processors detect that a geolocation of a software resource has changed to a new geolocation. In response to detecting that the geolocation of the software resource has changed to the new geolocation, the processor(s) apply a geolocation based resource policy to alter the software resource.

BACKGROUND

The present disclosure relates to the field of computing devices, andspecifically to computer resources utilized by computing devices. Morespecifically, the present disclosure relates to modifying a computerresource in response to a geophysical movement of the computer resource.

SUMMARY

A method, system, and/or computer program product modify a computerresource that has been moved to a new geolocation. One or moreprocessors detect that a geolocation of a software resource has changedto a new geolocation. In response to detecting that the geolocation ofthe software resource has changed to the new geolocation, theprocessor(s) apply a geolocation based resource policy to alter thesoftware resource.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an exemplary system and network in which the presentdisclosure may be implemented;

FIG. 2 illustrate a software resource being relocated to a newgeophysical location in accordance with one or more embodiments of thepresent invention;

FIG. 3 is a high-level flow chart of one or more steps performed by oneor more processors and/or other hardware devices to modify a computerresource that has been moved to a new geolocation;

FIG. 4 depicts a cloud computing environment according to an embodimentof the present invention; and

FIG. 5 depicts abstraction model layers of a cloud computer environmentaccording to an embodiment of the present invention.

DETAILED DESCRIPTION

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

With reference now to the figures, and in particular to FIG. 1, there isdepicted a block diagram of an exemplary system and network that may beutilized by and/or in the implementation of the present invention. Someor all of the exemplary architecture, including both depicted hardwareand software, shown for and within computer 101 may be utilized bysoftware deploying server 149 and/or software resource server(s) 153shown in FIG. 1 and/or the managing computer 201 shown in FIG. 2.

Exemplary computer 101 includes a processor 103 that is coupled to asystem bus 105. Processor 103 may utilize one or more processors, eachof which has one or more processor cores. A video adapter 107, whichdrives/supports a display 109 (which in one or more embodiments of thepresent invention is a touch-screen display capable of detecting touchinputs onto the display 109), is also coupled to system bus 105. Systembus 105 is coupled via a bus bridge 111 to an input/output (I/O) bus113. An I/O interface 115 is coupled to I/O bus 113. I/O interface 115affords communication with various I/O devices, including a keyboard117, a mouse 119, a media tray 121 (which may include storage devicessuch as CD-ROM drives, multi-media interfaces, etc.), a transceiver 123(capable of transmitting and/or receiving electronic communicationsignals), and external USB port(s) 125. While the format of the portsconnected to I/O interface 115 may be any known to those skilled in theart of computer architecture, in one embodiment some or all of theseports are universal serial bus (USB) ports.

As depicted, computer 101 is able to communicate with a softwaredeploying server 149 and/or other devices/systems using a networkinterface 129. Network interface 129 is a hardware network interface,such as a network interface card (NIC), etc. Network 127 may be anexternal network such as the Internet, or an internal network such as anEthernet or a virtual private network (VPN). In one or more embodiments,network 127 is a wireless network, such as a Wi-Fi network, a cellularnetwork, etc.

A hard drive interface 131 is also coupled to system bus 105. Hard driveinterface 131 interfaces with a hard drive 133. In one embodiment, harddrive 133 populates a system memory 135, which is also coupled to systembus 105. System memory is defined as a lowest level of volatile memoryin computer 101. This volatile memory includes additional higher levelsof volatile memory (not shown), including, but not limited to, cachememory, registers and buffers. Data that populates system memory 135includes computer 101's operating system (OS) 137 and applicationprograms 143.

OS 137 includes a shell 139, for providing transparent user access toresources such as application programs 143. Generally, shell 139 is aprogram that provides an interpreter and an interface between the userand the operating system. More specifically, shell 139 executes commandsthat are entered into a command line user interface or from a file.Thus, shell 139, also called a command processor, is generally thehighest level of the operating system software hierarchy and serves as acommand interpreter. The shell provides a system prompt, interpretscommands entered by keyboard, mouse, or other user input media, andsends the interpreted command(s) to the appropriate lower levels of theoperating system (e.g., a kernel 141) for processing. While shell 139 isa text-based, line-oriented user interface, the present invention willequally well support other user interface modes, such as graphical,voice, gestural, etc.

As depicted, OS 137 also includes kernel 141, which includes lowerlevels of functionality for OS 137, including providing essentialservices required by other parts of OS 137 and application programs 143,including memory management, process and task management, diskmanagement, and mouse and keyboard management.

Application programs 143 include a renderer, shown in exemplary manneras a browser 145. Browser 145 includes program modules and instructionsenabling a world wide web (WWW) client (i.e., computer 101) to send andreceive network messages to the Internet using hypertext transferprotocol (HTTP) messaging, thus enabling communication with softwaredeploying server 149 and other systems.

Application programs 143 in computer 101's system memory (as well assoftware deploying server 149's system memory) also include Logic forModifying a Software Resource (LMSR) 147. LMSR 147 includes code forimplementing the processes described below, including those described inFIGS. 2-3. In one embodiment, computer 101 is able to download LMSR 147from software deploying server 149, including in an on-demand basis,wherein the code in LMSR 147 is not downloaded until needed forexecution. In one embodiment of the present invention, softwaredeploying server 149 performs all of the functions associated with thepresent invention (including execution of LMSR 147), thus freeingcomputer 101 from having to use its own internal computing resources toexecute LMSR 147.

Also within computer 101 is a geolocation sensor 151, which is able todetect the physical location of computer 101 and/or the orientation ofcomputer 101. For example, geolocation sensor 151 may incorporate globalpositioning system (GPS) sensors that identify the geophysical locationof computer using signals from an array of space-based GPS satellites.Furthermore, location and positioning sensor 151 may identify a staticIP address of computer 101, which can be mapped to a physical location.

Also in communication with computer 101 are software resource server(s)153, which are hardware servers capable of serving (supplying)applications, databases, electronic files (e.g., text files, videofiles, audio files, etc.), virtual machines, etc.

The hardware elements depicted in computer 101 are not intended to beexhaustive, but rather are representative to highlight essentialcomponents required by the present invention. For instance, computer 101may include alternate memory storage devices such as magnetic cassettes,digital versatile disks (DVDs), Bernoulli cartridges, and the like.These and other variations are intended to be within the spirit andscope of the present invention.

The terms “location”, “geophysical location”, and “geolocation” are usedinterchangeably herein to describe a physical location of an object,such as a software resource stored on a storage device.

As described herein, the present invention provides a solution toappropriately modifying a software resource that has moved to adifferent geophysical location.

For example, a software resource (e.g., a text file, a database file, anaudio file, a video file, a virtual machine (i.e., software thatemulates a physical machine), etc.) may move from one physical locationto another (e.g., from one data center to another data center, from oneserver blade to another server blade, from one country to anothercountry, etc.). This movement (i.e., “migration”) may be physical (e.g.,physically moving a storage drive from one physical location to anotherphysical location) or electronic (e.g., transmitting the file over anetwork from one physical location to another physical location).

When such a movement/migration occurs, there may be a problem with thenew location. For example, assume that an electronic medical record(EMR) file for a patient is stored in a first country that has noregulations regarding storage/sharing of EMR files (i.e., the EMR can bestored anywhere and shared with anyone). Assume further that a secondcountry has very strict regulations regarding how the EMR is stored(e.g., encrypted, behind a firewall, etc.) and shared (e.g., with onlypredefined designated accessing parties). Thus, if anunencrypted/unsecured EMR is sent from the first country (where suchEMRs are permissible) to the second country (where such EMRs are notpermissible), then there is a problem. The present invention provides asolution to this problem.

With reference now to FIG. 2, assume that a software resource server 153a (analogous to one of the software resource server(s) 153 shown inFIG. 1) contains (stores) a set of software resources 202, such as thedepicted set of data files. The software resource server 153 a islocated in Zone A, which is a first geophysical location. In one or moreembodiments, the first geophysical location is determined by readingsfrom a geolocation sensor 251 a (analogous to geolocation sensor 151shown in FIG. 1).

Assume now that one of the set of software resources 202 (i.e., softwareresource 206 a) is migrated (copied and/or moved) to a second softwareresource server 153 b (also analogous to one of the software resourceserver(s) 153 shown in FIG. 1) within Zone B (a second geophysicallocation that is identified by geolocation sensor 251 b (also analogousto geolocation sensor 151 shown in FIG. 1). This migration results insoftware resource 206 b residing within the software resource server 153b in Zone B.

In one embodiment, software resource 206 a and software resource 206 bare a same copy of a same resource. That is, in this embodiment softwareresource 206 a moves from software resource server 153 a to softwareresource server 153 b, such that software resource 206 a no longerresides within the software resource server 153 a.

In one embodiment, software resource 206 a and software resource 206 bare different copies of a same resource. That is, in this embodiment acopy of software resource 206 a (software resource 206 b) is stored insoftware resource server 153 b, such that software resource 206 a isretained within the software resource server 153 a.

The present invention presents various methods for determining whetheror not the software resource 206 a has migrated from software resourceserver 153 a to software resource server 153 b (i.e., has migrated fromZone A to Zone B).

In one embodiment of the present invention, the migration from Zone A toZone B is detected when a relative location to another software resourcechanges. For example, assume that software resource 206 a is stored in amemory location that is X address lines away from software resource 208a in software resource server 153 a. Assume further that 1) softwareresource 208 b is X address lines away from software resource 206 b butis a different software resource than software resource 208 a (i.e.,software resource 208 a and software resource 208 b are differentsoftware resources), and/or 2) software resource 208 a and softwareresource 208 b are the same software resource but software resource 208b is now Y (instead of X) address lines away from software resource 206b. This indicates that software resource 206 b is not within thesoftware resource server 153 a, and thus is outside of Zone A. Byexamining the relative positions of software resources in varioussoftware resource servers, a managing computer 201 (analogous tocomputer 101 shown in FIG. 1) is able to determine the location (Zone B)of software resource server 153 b.

In one embodiment of the present invention, the locations of softwareresource server 153 a and software resource server 153 b are determinedby a global positioning system (GPS) satellite 210 interrogating andvalidating geolocation sensors 251 a-251 b (when architected as GPSpositioning sensors). That is, GPS satellite 210 determines thegeophysical location of geolocation sensor 251 a and geolocation sensor251 b. However, geolocation sensor 251 b could be a “fake” geolocationsensor that has been programmed to generate a false location signal.

For example, assume that geolocation sensor 251 b has been nefariouslyreplaced with a “fake” geolocation sensor, which outputs a locationsignal that reports, regardless of what GPS signal is being sent fromGPS satellite 210, that software resource server 153 b is currently inZone A (rather than accurately reporting that software resource server153 b is currently in Zone B). However, the original geolocation sensor251 b within software resource server 153 b was registered (e.g., usinga uniform universal identifier—UUID) with the managing computer 201,such that managing computer 201 only accepts GPS readings from theregistered original geolocation sensor 251 b, not the nefariousreplacement for geolocation sensor 251 b. If the managing computer 201receives a GPS signal from the nefarious replacement geolocation sensor,then managing computer 201 will assume that the software resource server153 b and software resource 206 b are in Zone B (or some other zoneother than Zone A), regardless of what geolocation signal is beingreceived from the replacement geolocation sensor.

Once a determination is made that the software resource 206 a/206 b hasmoved from Zone A to Zone B, various modifications/actions can be takenon software resource 206 b.

For example and in one embodiment of the present invention, in responseto determining that software resource 206 b is in Zone B, managingcomputer 201 (through whom all requests for software resource 206 b arehandled) will refuse to provide software resource 206 b to therequester.

In another embodiment of the present invention, in response todetermining that software resource 206 b is in Zone B, managing computer201 will modify software resource 206 b before sending it to therequester. For example, if software resource 206 b is an electronicmedical record (EMR), then managing computer 201 may redact certainprivileged/sensitive data from the EMR before sending it to therequester.

In another embodiment of the present invention, assume that the softwareresource 206 b is a virtual machine, and Zone B only has resourcescapable of supporting a certain version of the virtual machine. In thisscenario, the virtual machine will be modified accordingly by themanaging computer 201. For example, within Zone B there may be fewerprocessors, less storage space, etc. than are available within Zone A.As such, the virtual machine will be modified to be less powerful inZone B (e.g., has less bandwidth, is capable of executing fewerinstructions per second, etc.) than it was when configured for Zone A.

With reference now to FIG. 3, a high-level flow chart of one or moresteps performed by one or more processors and/or other hardware devicesto modify a computer resource that has been moved to a new geolocationis presented.

After initiator block 301, one or more processors (e.g., within managingcomputer 201 shown in FIG. 2) detect that a geolocation of a softwareresource (e.g., software resource 206 b) has changed to a newgeolocation (e.g., Zone B), as depicted in FIG. 2 and described in block303 in FIG. 3.

As described herein, in one embodiment of the present invention the newgeolocation is detected by a global positioning system (GPS) sensor(e.g., geolocation sensor 251 b shown in FIG. 2) that is incommunication with a GPS satellite (e.g., GPS satellite 210 shown inFIG. 2), where the GPS sensor is a component of a software resourceserver (e.g., software resource server 153 b shown in FIG. 2) thatcontains the software resource.

As described herein, in one embodiment of the present invention the GPSsensor is authenticated by a managing computer (e.g., managing computer201 shown in FIG. 2) that detects the geolocation of the softwareresource server by using GPS sensor readings from the GPS sensor. In anembodiment of the present invention, if the managing computer 201 doesnot authenticate the geolocation sensor 251 b (i.e., the GPS sensor inthe software resource server 153 b), then it will refuse to allow accessto the software resource 206 b, will modify the software resource 206 b,etc.

As described in block 305, in response to detecting that the geolocationof the software resource has changed to the new geolocation, theprocessor(s) apply a geolocation based resource policy to alter thesoftware resource.

The flow chart ends at terminator block 307.

In an embodiment of the present invention, the software resource is anelectronic file that was stored in a previous geolocation (e.g., such assoftware resource 206 a in Zone A, as shown in FIG. 2). As describedherein, the electronic file is from a first set of electronic files(e.g., set of software resources 202 shown in FIG. 2), where theelectronic file is a first electronic file (e.g., software resource 206a) that has a relative position to a second file (e.g., softwareresource 208 a) from the first set of electronic files. As shown in FIG.2, the first electronic file has been moved into a second set ofelectronic files (e.g., set of software resources 204 shown in FIG. 2)at the new geolocation. In this embodiment, one or more processors(e.g., within managing computer 201) determine a relative position ofthe first electronic file (e.g., software resource 206 b) to the secondelectronic file (e.g., software resource 208 b) from a second set ofelectronic files (e.g., set of software resources 204). The processor(s)determine that the relative position of the first electronic file to thesecond electronic file from the second set of electronic files isdifferent from the relative position of the first electronic file to thesecond electronic file from the first set of electronic files. Thus, inresponse to determining that the relative position of the firstelectronic file to the second electronic file from the second set ofelectronic files is different from the relative position of the firstelectronic file to the second electronic file from the first set ofelectronic files, the processor(s) determine that the geolocation of thesoftware resource has changed to the new geolocation and delete thefirst electronic file from the second set of electronic files.Alternatively, in response to determining that the relative position ofthe first electronic file to the second electronic file from the secondset of electronic files is different from the relative position of thefirst electronic file to the second electronic file from the first setof electronic files, the processor(s) block access to the firstelectronic file (e.g., for a requester of the first electronic file)from the second set of electronic files.

In an embodiment of the present invention, the software resource is anelectronic database, such that applying the geolocation based resourcepolicy deletes at least a portion of data in the electronic database.For example, assume that the electronic database is in a restrictedzone. As such, the processor(s) will delete any sensitive data (due toenterprise policies, regulations, laws, etc.) that are not permitted tobe electronically stored within that restricted zone. Alternatively,such sensitive data may be encrypted by the processor(s).

In an embodiment of the present invention, if the software resource hasbeen moved, then the managing computer will track the identity of anyonewho attempts to retrieve it after it has been moved. That is, in anembodiment of the present invention the software resource is anelectronic database in a database server, such that applying thegeolocation based resource policy causes the database server to: capturean identity of a requester of data from the electronic database; blockaccess by the requester to the electronic database; and report theidentity of the requester to a security management system.

In an embodiment of the present invention and as described herein, thesoftware resource is a virtual machine (VM), and applying thegeolocation based resource policy reduces a functionality of the VM(i.e., reduces its bandwidth, decreases the instructions per second thatit can process, etc. based on available supporting resources in the newlocation).

In an embodiment of the present invention, the software resource is anapplication, and applying the geolocation based resource policy reducesa functionality of the application. For example, if the application hasfeatures A, B, and C while maintained within Zone A shown in FIG. 2, itmay be modified to only have the features of A and C while within ZoneB. For example, assume that the software resource 206 a/206 b shown inFIG. 2 is a controller for a petrochemical refinery. While in Zone A,software resource 206 a will be able to control all actuators, fire upall furnaces, etc., as well as report conditions within a petrochemicalrefinery. However, while in Zone B, software resource 206 b will only beable to report conditions within petrochemical refinery, and will not beable to control actuators, furnaces, etc.

In an embodiment of the present invention, the software resource is adatabase in a database server, and applying the geolocation basedresource policy causes the database server to: delete an unauthorizedportion of the database, where the unauthorized portion has beenpredetermined to be unauthorized to be stored at the new geolocation;and retain an authorized portion of the database, where the authorizedportion has been predetermined to be authorized to be stored at the newgeolocation. That is, when software resource 206 a moves to Zone B (thusbecoming software resource 206 b), some of the data will remain withinsoftware resource 206 b while other data within software resource 206 awill be deleted from software resource 206 b.

In an embodiment of the present invention, the software resource is adatabase in a database server, and applying the geolocation basedresource policy causes the database server to label data from thedatabase with a sensitivity level tag, where the sensitivity level tagis based on a current geolocation of the database. That is, assume thatdata from software resource 206 a is never sensitive as long as it is inZone A. However, as soon as software resource 206 a migrates to Zone B(thus becoming software resource 206 b), some of the data becomes“sensitive”, due to legal restrictions, enterprise rules, etc. that areapplicable to Zone B. At that point, the managing computer 201 willlabel the data that is now “sensitive” accordingly.

In an embodiment of the present invention, the geolocation basedresource policy includes a set of actions to be carried out pergeolocation transition. That is, each action (deleting data, modifyingvirtual machines, encrypting data, etc. as described herein) will beperformed according to the particular location (e.g., “Zone”) in whichthe software resource is located. Such actions may therefore bedifferent for each particular location.

In an embodiment of the present invention, the software resource is anelectronic database, the geolocation based resource policy defines astate of availability for the data from the electronic database based ona current geolocation, and the state of availability is from a groupconsisting of the data being unencrypted, the data being encrypted, andthe data being unavailable in any form. That is, based on where thesoftware resource (e.g., data) has been migrated to, that data mayremain unencrypted, may be encrypted, or may be blocked from access atall, depending on the location at which it is currently residing (aftermigration).

In an embodiment of the present invention, assume that the softwareresource (e.g., a database) was in an original location (e.g., Zone A inFIG. 2) before moving to the new geolocation (Zone B). Assume furtherthat the software resource was in an unaltered state before moving tothe new geolocation. Assume further that one or more processors havedetected that the software resource has moved from the new geolocation(Zone B) back to the original location (Zone A). Thus in thisembodiment, in response to detecting that the software resource hasmoved from the new geolocation back to the original location, one ormore processors restore the software resource back to the unalteredstate. This can be accomplished by one of the set of software resources202 shown in FIG. 2 having a backup/mirror copy of the originalunaltered software resource, which is then used to restore the data.

The present invention may be implemented in one or more embodimentsusing cloud computing. Nonetheless, it is understood in advance thatalthough this disclosure includes a detailed description on cloudcomputing, implementation of the teachings recited herein are notlimited to a cloud computing environment. Rather, embodiments of thepresent invention are capable of being implemented in conjunction withany other type of computing environment now known or later developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 4, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-54Nshown in FIG. 4 are intended to be illustrative only and that computingnodes 10 and cloud computing environment 50 can communicate with anytype of computerized device over any type of network and/or networkaddressable connection (e.g., using a web browser).

Referring now to FIG. 5, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 4) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 5 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and computer resource modification processing96 to modify a computer resource that has been moved to a newgeolocation in accordance with one or more embodiments of the presentinvention as described herein.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the presentinvention. As used herein, the singular forms “a”, “an” and “the” areintended to include the plural forms as well, unless the context clearlyindicates otherwise. It will be further understood that the terms“comprises” and/or “comprising,” when used in this specification,specify the presence of stated features, integers, steps, operations,elements, and/or components, but do not preclude the presence oraddition of one or more other features, integers, steps, operations,elements, components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of various embodiments of the present invention has beenpresented for purposes of illustration and description, but is notintended to be exhaustive or limited to the present invention in theform disclosed. Many modifications and variations will be apparent tothose of ordinary skill in the art without departing from the scope andspirit of the present invention. The embodiment was chosen and describedin order to best explain the principles of the present invention and thepractical application, and to enable others of ordinary skill in the artto understand the present invention for various embodiments with variousmodifications as are suited to the particular use contemplated.

Any methods described in the present disclosure may be implementedthrough the use of a VHDL (VHSIC Hardware Description Language) programand a VHDL chip. VHDL is an exemplary design-entry language for FieldProgrammable Gate Arrays (FPGAs), Application Specific IntegratedCircuits (ASICs), and other similar electronic devices. Thus, anysoftware-implemented method described herein may be emulated by ahardware-based VHDL program, which is then applied to a VHDL chip, suchas a FPGA.

Having thus described embodiments of the present invention of thepresent application in detail and by reference to illustrativeembodiments thereof, it will be apparent that modifications andvariations are possible without departing from the scope of the presentinvention defined in the appended claims.

What is claimed is:
 1. A method comprising: detecting, by one or moreprocessors, that a geolocation of a software resource has changed to anew geolocation; and in response to detecting that the geolocation ofthe software resource has changed to the new geolocation, applying, byone or more processors, a geolocation based resource policy to alter thesoftware resource.
 2. The method of claim 1, wherein the new geolocationis detected by a global positioning system (GPS) sensor that is incommunication with a GPS satellite, and wherein the GPS sensor is acomponent of a software resource server that contains the softwareresource.
 3. The method of claim 2, wherein the GPS sensor isauthenticated by a managing computer that detects the geolocation of thesoftware resource server by using GPS sensor readings from the GPSsensor.
 4. The method of claim 1, wherein the software resource is anelectronic file that was stored in a previous geolocation, wherein theelectronic file is from a first set of electronic files, wherein theelectronic file is a first electronic file that has a relative positionto a second electronic file from the first set of electronic files,wherein the first electronic file has been moved into a second set ofelectronic files at the new geolocation, and wherein the method furthercomprises: determining, by one or more processors, a relative positionof the first electronic file to the second electronic file from a secondset of electronic files; determining, by one or more processors, thatthe relative position of the first electronic file to the secondelectronic file from the second set of electronic files is differentfrom the relative position of the first electronic file to the secondelectronic file from the first set of electronic files; and in responseto determining that the relative position of the first electronic fileto the second electronic file from the second set of electronic files isdifferent from the relative position of the first electronic file to thesecond electronic file from the first set of electronic files,determining, by one or more processors, that the geolocation of thesoftware resource has changed to the new geolocation and deleting, byone or more processors, the first electronic file from the second set ofelectronic files.
 5. The method of claim 1, wherein the softwareresource is an electronic file that was stored in a previousgeolocation, wherein the electronic file is from a first set ofelectronic files, wherein the electronic file is a first electronic filethat has a relative position to a second electronic file from the firstset of electronic files, wherein the first electronic file has beenmoved into a second set of electronic files at the new geolocation, andwherein the method further comprises: determining, by one or moreprocessors, a relative position of the first electronic file to thesecond electronic file from a second set of electronic files;determining, by one or more processors, that the relative position ofthe first electronic file to the second electronic file from the secondset of electronic files is different from the relative position of thefirst electronic file to the second electronic file from the first setof electronic files; and in response to determining that the relativeposition of the first electronic file to the second electronic file fromthe second set of electronic files is different from the relativeposition of the first electronic file to the second electronic file fromthe first set of electronic files, blocking, by one or more processors,access to the first electronic file from the second set of electronicfiles.
 6. The method of claim 1, wherein the software resource is anelectronic database, and wherein applying the geolocation based resourcepolicy deletes at least a portion of data in the electronic database. 7.The method of claim 1, wherein the software resource is an electronicdatabase, and wherein applying the geolocation based resource policyencrypts at least a portion of data in the electronic database.
 8. Themethod of claim 1, wherein the software resource is an electronicdatabase in a database server, and wherein applying the geolocationbased resource policy causes the database server to: capture an identityof a requester of data from the electronic database; block access by therequester to the electronic database; and report the identity of therequester to a security management system.
 9. The method of claim 1,wherein the software resource is a virtual machine (VM), and whereinapplying the geolocation based resource policy reduces a functionalityof the VM.
 10. The method of claim 1, wherein the software resource isan application, and wherein applying the geolocation based resourcepolicy reduces a functionality of the application.
 11. The method ofclaim 1, wherein the software resource is a database in a databaseserver, and wherein applying the geolocation based resource policycauses the database server to: delete an unauthorized portion of thedatabase, wherein the unauthorized portion has been predetermined to beunauthorized to be stored at the new geolocation; and retain anauthorized portion of the database, wherein the authorized portion hasbeen predetermined to be authorized to be stored at the new geolocation.12. The method of claim 1, wherein the software resource is a databasein a database server, and wherein applying the geolocation basedresource policy causes the database server to: label data from thedatabase with a sensitivity level tag, wherein the sensitivity level tagis based on a current geolocation of the database.
 13. The method ofclaim 1, wherein the geolocation based resource policy comprises a setof actions to be carried out per geolocation transition.
 14. The methodof claim 1, wherein the software resource is an electronic database,wherein the geolocation based resource policy defines a state ofavailability for the data from the electronic database based on acurrent geolocation, and wherein the state of availability is from agroup consisting of the data being unencrypted, the data beingencrypted, and the data being unavailable in any form.
 15. The method ofclaim 1, wherein the software resource was in an original locationbefore moving to the new geolocation, wherein the software resource wasin an unaltered state before moving to the new geolocation, and whereinthe method further comprises: detecting, by one or more processors, thatthe software resource has moved from the new geolocation back to theoriginal location; and in response to detecting that the softwareresource has moved from the new geolocation back to the originallocation, restoring, by one or more processors, the software resourceback to the unaltered state.
 16. A computer program product comprisingone or more computer readable storage mediums, and program instructionsstored on at least one of the one or more storage mediums, the storedprogram instructions comprising: program instructions to detect that ageolocation of a software resource has changed to a new geolocation; andprogram instructions to, in response to detecting that the geolocationof the software resource has changed to the new geolocation, apply ageolocation based resource policy to alter the software resource. 17.The computer program product of claim 16, wherein the software resourceis an electronic database, and wherein applying the geolocation basedresource policy encrypts at least a portion of data in the electronicdatabase.
 18. A computer system comprising one or more processors, oneor more computer readable memories, and one or more computer readablestorage mediums, and program instructions stored on at least one of theone or more storage mediums for execution by at least one of the one ormore processors via at least one of the one or more memories, the storedprogram instructions comprising: program instructions to detect that ageolocation of a software resource has changed to a new geolocation; andprogram instructions to, in response to detecting that the geolocationof the software resource has changed to the new geolocation, apply ageolocation based resource policy to alter the software resource. 19.The computer system of claim 18, wherein the software resource is adatabase in a database server, and wherein applying the geolocationbased resource policy causes the database server to: delete anunauthorized portion of the database, wherein the unauthorized portionhas been predetermined to be unauthorized to be stored at the newgeolocation; and retain an authorized portion of the database, whereinthe authorized portion has been predetermined to be authorized to bestored at the new geolocation.
 20. The computer system of claim 18,wherein the software resource is a database in a database server, andwherein applying the geolocation based resource policy causes thedatabase server to: label data from the database with a sensitivitylevel tag, wherein the sensitivity level tag is based on a currentgeolocation of the database.